Welcome Guest, you are in: Login
CTS Futures

Page History: Standard Header

Compare Page Revisions



« Older Revision - Back to Page History - Newer Revision »


Page Revision: 2012/09/05 18:07


All messages (administrative or application) are preceded by a Standard Header. In addition to providing the identification of FIX Session participants, the Standard Header identifies the Message Type (Tag 35), Message Length (Tag 9), Origination times (Tag 52 and Tag 122) and Message Sequence order (Tag 34). The Standard Header also offers additional information on FIX Session authentication, resent messages, duplicated messages and message routing and delivery.

Standard Header Dictionary

TagField NameReq'dComments
8BeginString YFIX.4.2 (Always unencrypted, must be first field in message)
9BodyLengthY(Always unencrypted, must be second field in message)
5MsgTypeY(Always unencrypted, must be third field in message)
9SenderCompIDY(Always unencrypted)
6TargetCompIDY(Always unencrypted)
15OnBehalfOfCompIDNTrading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
28DeliverToCompIDNTrading partner company ID used when sending messages via a third party (Can be embedded within encrypted data section.)
0SecureDataLenNRequired to identify length of encrypted section of message. (Always unencrypted)
1SecureDataNRequired when message body is encrypted. Always immediately follows SecureDataLen field.
4MsgSeqNumY(Can be embedded within encrypted data section.)
0SenderSubIDN(Can be embedded within encrypted data section.)
42SenderLocationIDNSender's LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
7TargetSubIDN“ADMIN” reserved for administrative messages not intended for a specific user. (Can be embedded within encrypted data section.)
43TargetLocationIDNTrading partner LocationID (i.e. geographic location and/or desk) (Can be embedded within encrypted data section.)
16OnBehalfOfSubIDNTrading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
44OnBehalfOfLocationIDNTrading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)
29DeliverToSubIDNTrading partner SubID used when delivering messages via a third party. (Can be embedded within encrypted data section.)
45DeliverToLocationIDNTrading partner LocationID (i.e. geographic location and/or desk) used when delivering messages via a third party. (Can be embedded within encrypted data section.)
3PossDupFlagNAlways required for retransmitted messages, whether prompted by the sending system or as the result of a resend request. (Can be embedded within encrypted data section.)|
7PossResendNRequired when message may be duplicate of another message sent under a different sequence number. (Can be embedded within encrypted data section.)
2SendingTimeY(Can be embedded within encrypted data section.)
22OrigSendingTimeNRequired for message resent as a result of a ResendRequest. If data is not available set to same value as SendingTime (Can be embedded within encrypted data section.)
12XmlDataLenNRequired when specifying XmlData to identify the length of a XmlData message block. (Can be embedded within encrypted data section.)
13XmlDataNCan contain a XML formatted message block (e.g. FIXML). Always immediately follows XmlDataLen field. (Can be embedded within encrypted data section.)
47MessageEncodingNType of message encoding (non-ASCII characters) used in a message’s “Encoded” fields. Required if any “Encoding” fields are used.
69LastMsgSeqNumProcessedNThe last MsgSeqNum value received by the FIX engine and processed by downstream application, such as trading system or order routing system. Can be specified on every message sent. Useful for detecting a backlog with a counterparty.
70OnBehalfOfSendingTimeNUsed when a message is sent via a “hub” or “service bureau”. If A sends to Q (the hub) who then sends to B via a separate FIX session, then when Q sends to B the value of this field should represent the SendingTime on the message A sent to Q. (always expressed in UTC (Universal Time Coordinated, also known as “GMT”)

FIX API Home Page.





Trade how you want, where you want

support@ctsfutures.com (312) 939 0164

2 Pierce Pl, Suite 200, Itasca, IL 60143

© 2009-2023 Cunningham Trading Systems LLC All rights reserved.